Provider Services API
Architecture Diagram
Search Before Create
| S. No. | Description - Search |
|---|---|
| 1 | LSC invokes the Process API to search for data in the MDM system. |
| 2 | Process API internally validates the received request and, if successful, invokes the System API. |
| 3 | System API internally invokes the MDM search endpoint, which then acknowledges the request and returns the relevant searched data. |
| 4 | In the System API, MDM data is formatted into LSC format before being forwarded to the Process API. |
| 5 | Respond back to LSC. |
| S. No. | Description - Download |
|---|---|
| 1 | LSC invokes the Process API to download main entity records from the MDM system. |
| 2 | Process API validates the request; if successful, it calls the System API |
| 3 | System API internally invokes the MDM download endpoint, which acknowledges the request and returns the relevant records for download. |
| 4 | System API transforms the data into LSC format before sending it to the Process API. |
| 5 | The main entity records are synchronously upserted into LSC, and their Salesforce IDs are concurrently stored. |
| 6 | Data is upserted into LSC |
| 7 | Upon successful upsertion of records, their Salesforce IDs are sent back to LSC. This triggers asynchronous post-processing, which includes: Contract Validation: Ensures all entities are under contract before further processing. Multi-level Relation Processing: Level 1: Processes immediate relationships (e.g., affiliations, workplace hierarchies). Level 2: Recursively processes related entities up to a configured depth. |
| 8 | Process API submits an asynchronous post-processing request to the System API. |
| 9 | System API forwards the request to MDM and receives the response. |
| 10 | Process API submits another request to the System API to download relation records. |
| 11 | System API downloads the relation records from MDM and forwards them to the Process API. |
| 12 | Process API then upserts the related and affiliation records into LSC. |
Data Change Request or Validation Request
| S. No. | Description - DCR Submission Job |
|---|---|
| 1 | Process API triggers a job at set intervals to retrieve Qualified DCR records from the LSC's Data Change Request entity. |
| 2 | Each record needs to be enriched with additional details from LSC entities like Account, ContactPointAddress etc., specifically the technical and business mandatory fields required by MDM. |
| 3 | Invoke the System API to transform the LSC request format into the MDM format using a custom mapping and also validate the request. |
| 4 | Forward the transformed and validated request to MDM, then receive their confirmation of processing. |
| 5 | Acknowledge the same from System API to Process API |
| 6 | Update the MDM status back to LSC's Data Change Request entity |
| S. No. | Description - DCR Monitoring Job |
|---|---|
| 1 | Process API triggers a job at set intervals to retrieve Processed DCR records from the LSC's Data Change Request entity. |
| 2 | Each record needs to be enriched with additional details from LSC entities like Account, ContactPointAddress etc., to know the Status of the DCR record from MDM. |
| 3 | Invoke the System API to transform the LSC request format into the MDM format. |
| 4 | Forward the transformed request to MDM, then receive their confirmation on approval or rejection. |
| 5 | Acknowledge the same from System API to Process API |
| 6 | Update the MDM status back to LSC's Data Change Request entity |